Build: Backport changelog generation from jQuery #251
Conversation
|
I think I prefer posting the generated changelog to github release notes. Do you agree? |
Yeah, that would be more similar to other projects; I just wander what to do with the legacy changelog entries. Should I just create releases on GitHub for them all and then drop the legacy changelog? |
|
I think you could just leave it for historical purposes and add a note to the top that says all release notes since are in GitHub releases. |
|
Cool, so are there any code changes needed beyond the note at the top? Keeping the |
|
I guess not. |
|
@timmywil I went ahead and copied all info from the old changelog to GitHub Releases: https://github.com/jquery/jquery-mousewheel/releases. This repo only has data for version 3.0.0 & up as previous ones were apparently not on Git so I posted all changelog entries up until 3.0.3 in a single entry; newer ones all have separate entries. I removed the legacy changelog from this PR. PTAL. |
2 participants
For some reason,
read -pdoesn't work in thepre-release.shscript - or at least that's my hypothesis why the script gets stuck onpre-release. I thought since Code is using it inpost-release.sh, it should also work inpre-release.sh, but maybe not?Hopefully, now it'll work. My previous testing was limited as dry-run doesn't show all these issues, so I merged the release-it PR and I tried to release an alpha for testing; that's when I hit the issue.
Backport the changelog generation script from jQuery Core.
Rename the oldMove currentCHANGELOG.mdtoLEGACY_CHANGELOG.mdto not lose it, but I'm contemplating moving it to GitHub Releases.CHANGELOG.mdentries to GitHub Releases.